Displaying targeted website content based on social user profile data

ABSTRACT

Displaying targeted website content based on social user profile data is disclosed. In some embodiments, the displaying of targeted website content based on social user profile data includes requesting social profile data for a user from an authentication provider using a token associated with the user; and generating a rule for web site customization using the social profile data.

BACKGROUND OF THE INVENTION

Various services such as Facebook®, Twitter®, Linkedin®, and othersexpose service APIs that adhere to various authentication protocols(e.g., OAuth 1.0/2.0, etc.) so that external websites or applicationsmay use such “trusted” services as sources of authorization andauthentication (in lieu of, or in addition to, their own internalauthentication mechanisms).

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a diagram illustrating an embodiment of an environment inwhich a system for displaying targeted website content based on socialuser profile data is used.

FIG. 2 is a block diagram illustrating an embodiment of a web experiencemanagement system.

FIG. 3 is a flow diagram illustrating an embodiment of a process forallowing a website to authenticate users based on an authenticationprotocol.

FIG. 4 is a diagram illustrating an embodiment of an interface forgenerating a Facebook® application.

FIG. 5 is a diagram illustrating an embodiment of an interface forgenerating a Twitter® application.

FIG. 6 is a diagram illustrating an embodiment of an interface for astabling a new group for social users.

FIG. 7A is a diagram illustrating an embodiment of an interface forcreating a Facebook® cloud service configuration.

FIG. 7B is a diagram illustrating an embodiment of an interface forcreating a Twitter® cloud service configuration.

FIG. 8 is a diagram illustrating an embodiment of an interface forapplying cloud service configurations to a website.

FIG. 9 is a flow diagram illustrating an embodiment of a process fordisplaying targeted website content based on social user profile data.

FIG. 10 is a flow diagram illustrating an embodiment of a process forobtaining social user profile data.

FIG. 11 is a diagram illustrating an embodiment of an interface forlogging into an Adobe CQ website using existing digital identities.

FIG. 12 is a diagram illustrating an embodiment of an interface forconfiguring a client context to display social profile data.

FIG. 13 is a diagram illustrating an embodiment of an interface forconfiguring a segment.

FIG. 14 is a diagram illustrating an embodiment of an interface forcreating a teaser.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Various services such as Facebook®, Twitter®, Linkedin®, and othersexpose service APIs that adhere to various authentication protocols(e.g., OAuth 1.0/2.0, etc.) so that external websites or applicationsmay use such “trusted” services as sources of authorization andauthentication (in lieu of, or in addition to, their own internalauthentication mechanisms).

Typically, however, it takes a significant amount of time for adeveloper of a website to implement and test code for each service thatthey wish to consume as an authentication source. This can make itdifficult to retrieve social user profile data from multiple “trustedservices” in order to provide targeted content to users. This can beinconvenient.

Thus, there is a need for an improved system that allows a website totake advantage of “trusted” services and effectively use informationsuch as social user profile data obtained from the “trusted” services todisplay targeted website content.

Accordingly, displaying targeted website content based on social userprofile data is disclosed in accordance with some embodiments.

FIG. 1 is a diagram illustrating an embodiment of an environment inwhich a system for displaying targeted website content based on socialuser profile data is used. In the example shown, “Bob” (102) is avisitor of the website for the sporting goods store, Geometrixx Outdoors(104), which is published using website experience management (WEM)system (106). In some embodiments, website (104) is an Adobe CQ websiteand WEM (106) is an Adobe CQ web experience management (WEM) system thatis used to author/publish website (104) as well as manage anddynamically determine and deliver personalized content. Website (104) isconfigured via WEM (106) by administrator (112). In various embodiments,administrator (112) is a website developer, digital marketer, or anyother appropriate administrator of website (104). For purposes ofillustration, embodiments employing an Adobe CQ web experiencemanagement system to author/publish an Adobe CQ website (“GeometrixxOutdoors”) are described in detail below. Other WEM systems orpublishing/authoring platforms can also be used.

In some embodiments, services 114 and 116 are digital identity platformsthat provide authentication services (e.g., via APIs) such that a memberof the platform can log onto and be authenticated by external websites(e.g., Adobe CQ website 104) using their existing digital identities.Examples of such digital identity platforms that provide authenticationservices include Facebook®, Twitter®, Linkedin®, Foursquare®, andothers. The digital identity platforms can each be associated withvarious authentication protocols (e.g., OAuth 1.0/2.0, etc.) so that anexternal Adobe CQ website (such as Geometrixx Outdoors 104) and WEM 106can use such “trusted” platforms as sources of authentication andauthorization (e.g., of resources of the trusted sites).

In some embodiments, Adobe CQ system 106 includes an authenticationconfiguration engine 108 that is configured to communicate with services114 and 116 and allows website 104 to authenticate users based onvarious authentication protocols. This can enable Bob, for example, tolog into the Geometrixx Outdoors website (104) using his existingFacebook® and/or Twitter® digital identities (i.e., federated identityor social login). Adobe CQ system 106 can also be authorized (e.g., byBob) to obtain resources (e.g., social profile data) from each ofservices 114 and 116 for providing targeted, personalized content (e.g.,as part of a marketing campaign) via social connect engine 110. In someembodiments, information associated with Adobe CQ system 106 is storedin storage unit 118. In various embodiments, storage unit 118 can be adatabase, flat file, or any other appropriate storage unit.

In some embodiments, the authentication and social connect engines areincluded as pluggable services (e.g., OSGi services) that can beintegrated as part of a website development process on Adobe CQ system106. As the authentication configuration process is integrated into awebsite publishing system such as Adobe CQ, connecting withauthentication providers such as Facebook® and Twitter® can besimplified in a manner that allows an Adobe CQ website (104) to beautomatically configured take advantage of trusted digital identityplatforms while minimizing the amount of authentication protocol andcoding knowledge (e.g., to handle handshakes, redirects, accessingsocial profile data, etc.) needed by administrators to implement theauthentication and login functionality. Additionally, in someembodiments, other publishing/authoring services such as marketingcampaign management services are included on publishing system 106 andare authorized to use information associated with authenticated usersthat is obtained from digital identity platforms such as services 110and 112 for providing personalized content to Bob.

In various embodiments, the elements of environment 100 communicate viaa network that comprises one or more of a wired network, a wirelessnetwork, a local area network, a wide area network, the Internet, or anyother appropriate network.

FIG. 2 is a block diagram illustrating an embodiment of a web experiencemanagement system. In some embodiments, system 200 of FIG. 2 is used toimplement Adobe CQ system 106 of FIG. 1. In the example shown, Adobe CQsystem 200 includes authentication configuration engine 202, socialconnect engine 204, and marketing campaign management engine 206. Invarious embodiments, engines 202, 204, and 206 comprise, as describedabove, pluggable services (e.g., OSGi services) that can be integratedinto an Adobe CQ system to communicate with each other as well as otherservices/components that can also be implemented on the Adobe CQ system.

Authentication configuration engine includes authentication handler 208,authentication library 210, and authentication service configurator 212.In some embodiments, authentication handler 208 includes authenticationhandlers to handle various authentication workflows (e.g., specializedauthentication handlers for OAuth 1.0/2.0, etc.). In some embodimentsauthentication library 210 includes libraries used to implement variousauthentication protocols/standards and communicate with various APIs(e.g., APIs for Google®, Yahoo®, Linkedin®, Twitter®, Foursquare®,Facebook®, etc.). In some embodiments, software development kits (SDKs)are also included, which can be used by administrators to configuretheir Adobe CQ websites as trusted authentication providers. Forexample, an administrator of Geometrixx Outdoors can allow users tocreate new digital identities and credentials for Geometrixx Outdoors,which can in turn be used to login to other third party websites.

In some embodiments, authentication service configurator 212 is used toconfigure services that are used to communicate with variousauthentication providers (e.g., Facebook®, Twitter®, etc.). In someembodiments, an authentication service is configured for each digitalidentity platform that an Adobe CQ website (e.g., website 104 of FIG. 1)is configured to communicate with and authenticate users. More than oneauthentication service can also be configured for a singleauthentication provider (e.g., that includes differentsettings/configurations).

The authentication services can be configured to include details ofapplications created at authentication providers, which will bedescribed in more detail below. In various embodiments, serviceconfigurations include permissions to be requested of authenticatedusers, such as credentials (e.g., username and password), resourceswhich an Adobe CQ website such as Geometrixx Outdoors is authorized toaccess (e.g., Facebook® likes, interests, profile information, friends,Twitter® feeds, followers, etc.) as well as actions that GeometrixxOutdoors can perform on behalf of the user (e.g., post a status updateon behalf of a Facebook® user or a tweet on behalf of a Twitter® user).In some embodiments, authentication service configurations include usergroups (e.g., CQ authentication user groups) that a visitor can begrouped into based on the digital identity platform that they havelogged into the Adobe CQ website with. The user groups (e.g., CQ usergroups) can be used by other components of an Adobe CQ system, such as amarketing campaign management component to provide a personalized webexperience. In some embodiments, authentication service configurationsare associated with, or otherwise applied to, particular portions of anAdobe CQ website or content management system (such as Adobe CQ). Forexample, Adobe CQ website 104 of FIG. 1 could include an Italian portionof the website, whose Facebook® authentication service is configureddifferently to the Facebook® authentication service applied to theFrench portion of the website. For example, the two services, althoughboth associated with Facebook®, could be configured differently andrequest authorization for access to different resources due to culturalprivacy concerns. Different portions of a website can also be associatedwith different authentication providers as well. For example, ifGeometrixx Outdoors is configured to allow a user to login using theirFacebook®, Twitter®, and Linkedin® digital identities, the shoppingportion of Geometrixx Outdoors could be allowed to have access toFacebook® and Twitter® social profile data, while a “jobs” portion ofthe website could be allowed to have access to a user's Linkedin® socialprofile data.

Social connect engine 204 includes client context engine 214 andrule/segment engine 216. Social connect engine 204 can be used to allowusers to connect to and manage connections with various digital identityplatforms. In some embodiments, client context engine 214 is a contentmanagement component configured to read authorized user profile data ofthe digital identities that a user has logged in with (e.g., Facebook®,Twitter® social profile data) to generate a new profile of the user. Theuser profile data can then be mapped to a segment (i.e., to segment theuser) which will be described in more detail below. In some embodiments,determinations of what content to display or rendered to a user are madebased at least in part on the segmenting of the user. The informationincluded in the client context can be used by various components (e.g.,marketing campaign management component 206) of a WEM such as Adobe CQto provide a user with targeted, personalized content. In someembodiments, the client context information is stored or otherwisemaintained on the side of the user visiting the Adobe CQ website (e.g.,within the browser of the visitor).

Rule/segment engine 216 is configured to facilitate the generation ofsegments and rules based on user profile data obtained from one or moreexisting digital identities of authenticated users (e.g., social profiledata) and allows the segments and rules to be associated with oneanother to be interpreted by components such as client context engine214 and marketing campaign management engine 206. In some embodiments,segments are used to segment the user into a particular bucket in orderto provide a visitor, such as Bob, with targeted and personalizedcontent that is maintained in the marketing campaign management sectionof an Adobe CQ system. In some embodiments, segments are collections ofone or more rules/traits. In some embodiments, rules are definedconditions (or traits of interest) associated with or generated fromobtained information that when matched or triggered on, can be used toidentify users and provide targeted/personalized content. Examples ofrules/traits include “gender=male,” “Facebook® like=snow,” “Facebook®interest=snowboarding,” “Twitter® follower of =Shaun White.” Segmentscan then be generated from defined rules to segment a user into aparticular bucket that can be associated with candidatecontent/experiences. Example candidate content/experiences includeteasers/paragraphs to be displayed/rendered (e.g., used to steerspecific visitor segments to content that is focused on theirinterests), newsletters, e-mail communications, content used for testingand targeting (e.g., for use by a marketer as a tool to optimize awebsite to provide more relevant content and offers by designing andexecuting tests, creating audience segments, targeting content, etc.),or any other appropriate candidate content/experiences. As an example, asegment including the rules “gender=male,” “like=formula 1,” and “fan of=Ayrton Senna,” can be created, and users who match this segment andcollection of rules are shown a particular teaser out of a number ofcandidate teasers associated with various marketing campaigns (e.g.,formula 1 racing teaser instead of hiking teaser).

Marketing campaign management engine 206 is an example component of anAdobe CQ system that can take advantage of integration withauthentication engine 202 and social connect engine 204 to dynamicallydetermine and deliver targeted and personalized content (e.g., teaser orad or customized website) to a visitor such as Bob (i.e., in the contextof Bob as a visitor) of an Adobe CQ website who has logged into theAdobe CQ website and been authenticated using existing digitalidentities such as their Facebook® and Twitter® logins and credentials.

FIG. 3 is a flow diagram illustrating an embodiment of a process forallowing an Adobe CQ website to authenticate users based on anauthentication protocol (e.g., OAuth 1.0/2.0, etc.). In someembodiments, process 300 of FIG. 3 is executed by authenticationconfiguration engine 202 of FIG. 2. The process begins at 302 when anauthentication package is installed. Packages and code used to implementauthentication mechanisms can be installed as a pluggable service (e.g.,as pluggable OSGi service) of a web authoring platform (e.g., Adobe CQ).The installed packages can include default packages that arepreconfigured to connect with digital identity platforms (e.g.,Facebook® or Twitter®) that utilize particular authentication protocolsor mechanisms (e.g., OAuth 2.0 or 1.0). The installed packages can alsoinclude tools (e.g. SDKs) for developers to configure connections forother digital identity providers.

At 304, an authentication handler is configured to handle theauthentication workflow of an authentication provider (e.g., OAuth 1.0for Twitter®, OAuth 2.0 for Facebook®, etc.).

At 306, an application associated with an authentication provider (e.g.,Facebook®, Twitter®, etc.) is generated. In some embodiments, anapplication is generated in order to make a Adobe CQ website (e.g.,Geometrixx Outdoors) known to the authentication provider so that theAdobe CQ website and the authentication provider are connected to allowfor authentication, authorization, and exchange of information betweenthe two entities. For example, a properly configured Facebook®application (e.g., via Facebook® connect) enables Facebook® social loginand connection. In some embodiments, a user, such as administrator 112of FIG. 1 is prompted to generate an application at the authenticationprovider. In some embodiments, one or more keys are provided in responseto generating an application. For example, when generating a Facebook®application, an application id and secret are provided.

At 308, a group of users is established. In various embodiments,existing user groups (e.g., CQ user group) can be leveraged or a newuser group can be created specifically for users. For example, Facebook®users and Twitter® users can be included in a group called “fbusers” or“Twitter® users,” respectively, or can be included in a general socialusers group. In some embodiments, all users are included in a general“social users” group.

At 310, a service configuration associated with an authenticationprovider is generated. The service configuration is set up by anadministrator of an Adobe CQ system to enable authentication with aparticular authentication provider for which an application has beencreated. The service configuration includes the details of theapplication created (e.g., keys), permissions requested (i.e.,authorized resources), and the CQ user group to be used for new userswho login via the authentication provider. The permissions requested caninclude basic permissions as well as additional extended permissionsthat can be specified by the authentication provider as options. Eachauthentication provider can have a unique and special set of permissionsthat specifically relate to their digital identity platform.

At 312, a service configuration is applied to a portion of an Adobe CQwebsite. As described in the example above, if an Adobe CQ website suchas Geometrixx Outdoors included French, German, and Italian portions ofthe website, different credentials and resources could be requested fromFacebook® for the French and German site than the Italian site, whichwould be automatically/dynamically configured and specified by usingspecialized service configurations/settings while minimizing specializedcode development. In some embodiments, portions of the website can alsobe associated with different authentication providers via serviceconfigurations so that a user can use various authentication providersfor logging into the website.

FIG. 4 is a diagram illustrating an embodiment of an interface forgenerating a Facebook® application. In the example shown, an App ID andApp Secret (402) are provided for accessing Facebook®. At 404, thewebsite utilizing Facebook® login (e.g., Geometrixx Outdoors) isentered.

FIG. 5 is a diagram illustrating an embodiment of an interface forgenerating a Twitter® application.

FIG. 6 is a diagram illustrating an embodiment of an interface forestablishing a new group for social users (e.g., new CQ User Group forgeneral “socialusers” including Facebook®, Twitter®, Linkedin® users,etc.).

FIG. 7A is a diagram illustrating an embodiment of an interface forcreating a Facebook® cloud service configuration. In the example shown,the App ID and Secret provided when generating the Facebook® Applicationare entered into the Facebook® service configuration. “fbusers” (704) isan example user group (e.g., CQ user group) that authenticated users whologin via Facebook® are added to. As described above, the group can bean existing group or a new group that was established via the interfaceas shown in FIG. 6. Example user permissions (e.g., basic or defaultpermissions) such as “user about me, user activities, user birthday,user interests, user likes, etc.” are shown at 706. Extended permissionsare also shown, which may be further requested from a user upon login.

FIG. 7B is a diagram illustrating an embodiment of an interface forcreating a Twitter® cloud service configuration

FIG. 8 is a diagram illustrating an embodiment of an interface forapplying cloud service configurations to a website. In the exampleshown, Facebook® Connect and Twitter® Connect cloud serviceconfigurations (802) are applied to the Geometrixx Outdoors Site (804)via the interface. Service configurations (with potentially differentsettings) can also be applied to other portions of the Adobe CQ website,such as the Geometrixx Outdoors mobile site.

FIG. 9 is a flow diagram illustrating an embodiment of a process fordisplaying targeted website content to an Adobe CQ website visitor basedon social user profile data. In some embodiments, process 900 isexecuted by social connect engine 204 and marketing campaign managementengine 206 of FIG. 2. The process begins at 902 when social profile datais requested and received, as will be described in more detail below.

At 904, rules and segments are generated. As described above, rules andsegments can be generated using social profile data and used to segmentusers into various buckets in order to allow for dynamic websitecustomization and to provide targeted and relevant content to users(e.g., as part of a targeted marketing campaign). In variousembodiments, generating a segment includes entering a title for the newsegment (e.g., “Snowboarders”) and configuring properties of thesegment, which can be based on obtained social profile data specifyingparticular rules or traits of interest. For example, the “Snowboarders”segment can be configured to include generated rules such as “Facebook®interest=snowboarding,” “Favorite Athlete=Shaun White,” etc.

At 906, a segment (and its associated collection of rules) is associatedwith a campaign. For example, because the winter season is approaching,a digital marketer associated with Geometrixx Outdoors can decide tobegin a new marketing campaign associated with winter sports. Increating the new marketing campaign, the digital marketer can createvarious teasers or banners associated with snowboarding, skiing, etc. Inorder to provide the appropriate and relevant teaser to a visitor ofGeometrixx Outdoors, the digital marketer can associate the snowboardingcampaign teaser with the snowboarding segment generated above.

At 908, content is provided to an Adobe CQ website visitor. Using thesegments and campaigns described above, authenticated visitors of anAdobe CQ website can be targeted and provided relevant content based onobtained social profile data and their client context (i.e., provide acustomized website tailored with respect to, or dynamicallydisplayed/rendered in the context of the visitor). For example, anauthenticated visitor whose Facebook® profile information matches asnowboarding segment can be displayed/rendered a snowboarding teaserupon logging into the Geometrixx Outdoors website using their Facebook®credentials.

In some embodiments an administrator can simulate how the website wouldbe rendered in the context of various users and can view the socialprofile data for a specific user by configuring an existing clientcontext by adding various social components (e.g., Facebook® interests,demographics, etc.) and then specifically loading the stored user'sprofile into the client context for the simulation and testing ofvarious campaign segments and traits.

FIG. 10 is a flow diagram illustrating an embodiment of a process forobtaining social user profile data. In some embodiments, process 1000 isused to implement process step 902 of FIG. 9. The process begins at 1002when an indication of a login to a digital identity platform by a useris received (e.g., user has logged into Geometrixx Outdoors via theirexisting Facebook® or Twitter® digital identity).

At 1004, the user is authenticated. The user can be authenticated viaauthentication configuration engine 202 of FIG. 2.

At 1006, authorization to access resources is requested. In someembodiments, if the user is a new user, they are prompted to indicatewhat resources the Adobe CQ website is authorized to access and obtainfrom an external digital identity platform. In some embodiments, theresources requested are specified in a previously generated applicationservice configuration (e.g., basic/extended permissions (706) of FIG.7A).

At 1008, an access token is received from an authenticationprovider/digital identity platform. The access token can be associatedwith a set of access permissions indicating the resources to whichauthorization has been granted (e.g., Facebook® likes, friends,interests, Twitter® followers, hash tags, etc.).

At 1010, user information is obtained. In some embodiments, userinformation is obtained from an authentication provider via the accesstoken provided by the authentication provider. In some embodiments, userinformation is obtained via a graph API associated with anauthentication provider (e.g., Facebook® social graph API). In someembodiments, the obtained user information/social profile data is storedwith a user profile (e.g., Adobe CQ user profile). In some embodiments,the obtained user information/social profile data can beconfigured/specified to be stored using tags that can be stored in atagging infrastructure. For example, “likes” and “interests” obtainedfrom a user's Facebook® profile can be tagged and stored in a centralAdobe CQ tagging infrastructure. Tags can then be taken advantage of andused throughout the Adobe CQ environment (e.g., by marketing campaignmanagement component or any other appropriate CQ component) to determinewhat content should be targeted upon. Social profile data can beassigned to a particular tag and reused. For example, if a tag for “UCBerkeley” was previously stored in the tagging infrastructure, in theevent that a new user logged in via Facebook® and was indicated to go to“UC Berkeley,” a new tag would not have to be created, and the profileof the user can be associated with the existing “UC Berkeley” tag.Information obtained for different digital identity platforms can alsobe grouped in various ways. For example, all tags generated fromFacebook® and Twitter® information can be grouped into a single “socialtags” bucket, with duplicates removed as needed, or the tags may remainseparate and distinct from each other (e.g., one location for Facebook®tags, separate location for Twitter® tags). The grouping of informationobtained for different digital identity platforms can bespecified/implemented via authentication handler 208.

At 1012, a client context for the user is generated. In someembodiments, the client context includes a user profile generated usingdata (e.g., social profile data) obtained from external digital identityplatforms. The user profile can be configured to display social profiledata (e.g., age, favorite quote, books, likes, interests). The socialprofile data can be applied to the client context automatically or by anadministrator of the Adobe CQ system. Tags can also be applied to theclient context. As described above, the client context can reside in abrowser of the Adobe CQ website visitor, with an Adobe CQ user profilefor the visitor also stored on the side of the Adobe CQ system.Personalized content can be provided to the visitor based on theirclient context and user profile. In some embodiments, profile simulationcan be performed for testing purposes by configuring a client context indifferent ways and loading and simulating a client context user profileon any page (e.g., in a web experience management system on an Adobe CQsystem) to see what content will be provided to them.

Facebook®Facebook®Facebook®Facebook®FIG. 11 is a diagram illustrating anembodiment of an interface for logging in to an Adobe CQ website usingexisting digital identities. In the example shown, the visitor can loginwith one or more of their Facebook® digital identity, Twitter® identity,or Geometrixx Outdoors identity (e.g., if Adobe CQ website has internalmechanism for authentication/credentials). In some embodiments, the useris presented with additional prompts requesting authorization toresources (e.g., likes, favorites, interests, friends, etc.). In someembodiments, a first prompt for basic permissions is displayed to auser, and a second prompt that includes extended permissions ispresented to a user. In some embodiments, the request for authorizationto access resources is presented the first time a user has logged ontoan Adobe CQ website. In some embodiments, a user profile is not storedin the event that a user does not complete the login procedure or onlypartially completes the login procedure (e.g., cancelling login beforeall prompts/requests have been accepted).

FIG. 12 is a diagram illustrating an embodiment of an interface forconfiguring a client context to display social profile data. In theexample shown, various user information and social profile data displaycomponents can be added to the client context. For example, in theinterface shown, Facebook® Interests component (1202) can be added tothe client context via drag and drop (1204). Other social profile datacomponents can also be added to the client context at the same time.

FIG. 13 is a diagram illustrating an embodiment of an interface forconfiguring a segment. In the example shown, a segment for snowboardingis being generated. Various rules/traits can be selected to define thesegment. For example, traits associated with Facebook® interests (e.g.,interest=snowboarding) can be added to the segment.

FIG. 14 is a diagram illustrating an embodiment of an interface forcreating a teaser. In the example shown, the teaser leverages segments(1402) and social profile data. The teaser can be associated with amarketing campaign, managed by, for example, the marketing campaignmanagement component of an Adobe CQ system.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A method comprising: receiving, at a web server,a request to access a web page provided by the web server, the requestcomprising a user login identity for logging a user into the web page,the user login identity authenticating the user based on a separateaccount managed by an authentication provider different and separatefrom the web server; requesting and receiving, at the web server, socialprofile data for the user from the authentication provider using theuser login identity; identifying, at the web server, a segment bydetermining that the social profile data satisfies a plurality ofconditions specified by a plurality of rules for the segment, whereinthe segment indicates an attribute common to a plurality of separateaccounts managed by one or more authentication providers, wherein thesegment comprises the plurality of rules, wherein each rule specifies atleast one condition from the plurality of conditions, and whereinidentifying the segment comprises: generating a user profile based onthe social profile data; storing the user profile locally at the webserver; and selecting the segment from a plurality of segments based ondetermining that data from the user profile satisfies the plurality ofconditions specified by the plurality of rules for the segment;identifying, at the web server, personalized content based on theattribute indicated by the segment; and providing, at the web server,the personalized content as part of the web page provided by the webserver.
 2. The method of claim 1, wherein each rule defines a conditioncomprising a trait with an assigned value obtained from social profiledata from a plurality of user login identities.
 3. The method of claim1, wherein determining that the social profile data satisfies theplurality of conditions comprises: matching the social profile data tothe plurality of conditions specified by the plurality of rules for thesegment.
 4. The method of claim 1, wherein providing personalizedcontent comprises: selecting a group of potential advertisementsassociated with the segment identified.
 5. The method of claim 1,wherein personalized content comprises a teaser, a newsletter, anadvertisement, a customized web page, or an e-mail communication to beprovided as part of the web page by the web server.
 6. The method ofclaim 1, wherein the segment is identified from a plurality of segments,each of the segments generated based on a plurality of social profiledata associated with a plurality of authentication providers.
 7. Themethod of claim 1, wherein identifying the personalized content furthercomprises: matching the segment to a group of segments associated with agroup of user profiles, the user profiles stored locally at the webserver and generated based on a set of social profile data of aplurality of users, the set of social profile data received from aplurality of authentication providers; and selecting the personalizedcontent based on the matching.
 8. The method of claim 7, wherein thesegment is associated with a tag generated based on the social profiledata and indicating a particular interest, and wherein identifying thepersonalized content comprises: matching the tag to another tagassociated with the group of segments, the other tag generated based onthe set of social profile data of the plurality of users and indicatinga common interest of the plurality of users; and selecting thepersonalized content based on the matching, wherein the personalizedcontent is associated with the group of segments.
 9. The method of claim1, further comprising determining an interest based on the segment,wherein the web site comprises another web page configured to be loggedinto based on the user login identity, wherein logging the user into theweb page comprises: determining whether the separate account managed bythe authentication service provider is usable to access the web page;logging in the user into the web page if the separate account is usableto access the web page; and logging in the user into the other web pageif the separate account is unusable to access the web page, wherein theother web page is logged into based on the separate account andpersonalized based on the interest that is associated with the separateaccount.
 10. The method of claim 1, wherein the web site comprisesanother web page configured to be logged into based on the user loginidentity, and further comprising: using the user login identity to login the user into the other web page; contacting the authenticationprovider to request and receive a different set of user profile databased on the separate account and the other web page; and personalizingcontent of the other web page based on the different set of user profiledata.
 11. The method of claim 1, wherein the plurality of rulesspecifies a condition based on a source of the social profile data, andwherein identifying the segment comprises: determining that theauthentication provider is the source of the social profile data;applying the condition to the social profile data based on thedetermining; and matching the user profile to the segment based on thesocial profile data satisfying the condition.
 12. The method of claim 1,wherein the attribute represents a trait and an interest common acrossthe plurality of separate user accounts, wherein a first rule of theplurality of rules specifies a first condition for social profile dataretrieved from a first authentication provider to meet the trait,wherein a second rule of the plurality of rules specifies a secondcondition for social profile data retrieved from a second authenticationprovider to meet the interest, and wherein identifying the segmentcomprises matching the user profile to the segment based on the socialprofile data of the user satisfying the first condition and the secondcondition.
 13. A computer program product comprising a non-transitorycomputer-readable medium embodying program instructions that, whenexecuted by a system, cause the system to perform operations comprising:receiving, at a web server, a request to access a web page provided bythe web server, the request comprising a user login identity for logginga user into the web page, the user login identity authenticating theuser based on a separate account managed by an authentication providerdifferent and separate from the web server; requesting and receiving, atthe web server, social profile data for the user from the authenticationprovider using the user login identity; identifying, at the web server,a segment by determining that the social profile data satisfies aplurality of conditions specified by a plurality of rules for thesegment, wherein the segment indicates an attribute common to aplurality of separate accounts managed by one or more authenticationproviders, wherein the segment comprises the plurality of rules, whereineach rule specifies at least one condition from the plurality ofconditions, and wherein identifying the segment comprises: generating auser profile based on the social profile data; storing the user profilelocally at the web server; and selecting the segment from a plurality ofsegments based on determining that data from the user profile satisfiesthe plurality of conditions specified by the plurality of rules for thesegment; identifying, at the web server, personalized content based onthe attribute indicated by the segment; and providing, at the webserver, the personalized content as part of the web page provided by theweb server.
 14. The computer program product of claim 13, wherein eachrule defines a condition comprising a trait with an assigned valueobtained from social profile data from a plurality of user loginidentities.
 15. The computer program product of claim 13, whereindetermining that the social profile data satisfies the plurality ofconditions comprises: matching the social profile data to the pluralityof conditions specified by the plurality of rules for the segment. 16.The computer program product of claim 13, wherein providing personalizedcontent comprises: selecting a group of potential advertisementsassociated with the segment identified.
 17. A system comprising aprocessor and a non-transitory computer-readable medium, wherein thenon-transitory computer-readable medium embodies one or more programcomponents that configure the computing system to carry out operationscomprising: receiving, at a web server, a request to access a web pageprovided by the web server, the request comprising a user login identityfor logging a user into the web page, the user login identityauthenticating the user based on a separate account managed by anauthentication provider different and separate from the web server;requesting and receiving, at the web server, social profile data for theuser from the authentication provider using the user login identity;identifying, at the web server, a segment by determining that the socialprofile data satisfies a plurality of conditions specified by aplurality of rules for the segment, wherein the segment indicates anattribute common to a plurality of separate accounts managed by one ormore authentication providers, wherein the segment comprises theplurality of rules, wherein each rule specifies at least one conditionfrom the plurality of conditions, and wherein identifying the segmentcomprises: generating a user profile based on the social profile data;storing the user profile locally at the web server; and selecting thesegment from a plurality of segments based on determining that data fromthe user profile satisfies the plurality of conditions specified by theplurality of rules for the segment; identifying, at the web server,personalized content based on the attribute indicated by the segment;and providing, at the web server, the personalized content as part ofthe web page provided by the web server.
 18. The system of claim 17,wherein each rule defines a condition comprising a trait with anassigned value obtained from social profile data from a plurality ofuser login identities.
 19. The system of claim 17, wherein determiningthat the social profile data satisfies the plurality of conditionscomprises: matching the social profile data to the plurality ofconditions specified by the plurality of rules for the segment.
 20. Thesystem of claim 17, wherein providing personalized content comprises:selecting a group of potential advertisements associated with thesegment identified.